Channel Settings

adminEmailAddress

Email address of the site administrator. The system sends important

notifications, such as background task failures, to this address.

customerServiceEmailAddress

Email address of the back-office customer service person or alias (e.g. Service@YourCompany.com). If not specified, the system uses the value of the "from" attribute of the <smtp> child element of the <mailSettings> element.

defaultLanguage

Specifies the default language for the channel. If not specified, the system uses "eng" for English. If specified, the value must be one of the following: eng,zho,dan,nld,fin,fra,deu,ita,kor,por,spa,swe,tur

registrationType

Registration method for the website. This attribute is required. Possible types are "None", "Public", "Request", and "Token".

None - New users are not allowed to register. This is typically used when the site is to be restricted to only those users setup exclusively by Administrators.

Public - New users can register and gain immediate access to the website.

Request - A user provides registration information and an email is sent to the back-office for approval. Administrators would then setup the user and notify the user when they can log on to the site.

Token - A user has been previously sent a registration token representing their existing company account. They enter this token along with their company number, plus their contact information. If the decrypted token matches the entered company account number, a new contact is created for the specified company. This option requires some coordination between your marketing department and Kore in order to generate the tokens to be sent to existing customers.

newAccountTemplateNo

Identifier of the template to use when formatting emails sent to end-users that provides information for accessing a new account. Value must be the identifier of a valid notification template in the system. If specified, the value must be the NotificationTemplateNo in KsNotificationTemplates. If not specified, an error is logged and no email is sent. Refer to the Notification Template Listing topic for more information.

applicationRootUrl

The URL of the root of the web site. This is typically referenced in Notification Templates as a substitution parameter (i.e. @KSsystem.ApplicationRootURL) to specific image paths, page links, etc. Various background processes in KommerceServer that send e-mails do not operate under an interactive web context and therefore relative paths will not work in the templates. Instead, an absolute path is required. By using a substitution parameter, the templates are more portable between multiple websites or in the event the website domain is changed.

requestAccountTemplateNo

Identifies the notification template to use when formatting emails sent to the back-office that provides information needed to evaluate and create a new account. This setting is used in conjunction with the registrationType setting of “Request”. If specified, the value must be the NotificationTemplateNo of an existing Notification Template. If not specified, an error is logged and no email is sent.
Note: If a notification template is used, the object context for the template should be based on Person.AccountRequest.AccountRequest.

resetPasswordTemplateNo

Identifies the notification template to use when formatting emails sent to end-users that provides information for resetting a password. If specified, the value must be the NotificationTemplateNo for an existing Notification Template. If not specified, an error is displayed, the error is logged, and no email is sent.
Note: If a notification template is used, the object context for the template should be based on KSUser.KSUser.

transactionRootTag

The root element name to use for all posted XML messages. Posting of transactional messages is setup using the Events & Actions system in KommerceServer and is used for integration purposes. If a non-empty value is specified, the system will envelop each posted XML message with an element by this name. If the value is empty, the system will not add an additional enclosing root element to the transaction XML. For most integrations using Kourier in the back office, this setting should be “KommerceServer”.

transactionTag

The transaction element to use for all posted XML messages. Posting of transactional messages is setup using the Events & Actions system in KommerceServer and is used for integration purposes. If a non-empty value is specified, the system will envelop each posted XML message with an element by this name. This setting is for the DataFlo ERP system primarily for downward compatibility for a previous version of KommerceServer that supported multiple transactions per XML message. This is no longer supported as there is a 1-to-1 ratio between a single transaction per XML message posted.